Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9ac15edc0c1bffb1d9b684becd9c9035c7a974efa77d9d3c1df2fdc8adcdbfe5

Tx prefix hash: f9ec59cfaff2a2ebfc07cd1772ed3bc8ec2f70252617a2eabc1ccf0973ceb05d
Tx public key: ec80f85349d0d1a59146442461072f65a1b737319e0aedf4bdf54d0eee43ec3b
Timestamp: 1704537039 Timestamp [UCT]: 2024-01-06 10:30:39 Age [y:d:h:m:s]: 01:097:11:34:16
Block: 929339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330789 RingCT/type: yes/0
Extra: 01ec80f85349d0d1a59146442461072f65a1b737319e0aedf4bdf54d0eee43ec3b02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b72d4742010cf968d82460a6375da3646db07dbd8499bf13a7b989d7962bd01 0.600000000000 1387211 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 929349, "vin": [ { "gen": { "height": 929339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b72d4742010cf968d82460a6375da3646db07dbd8499bf13a7b989d7962bd01" } } ], "extra": [ 1, 236, 128, 248, 83, 73, 208, 209, 165, 145, 70, 68, 36, 97, 7, 47, 101, 161, 183, 55, 49, 158, 10, 237, 244, 189, 245, 77, 14, 238, 67, 236, 59, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8