Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a15f6d67bfdc6280a476c30271ad397d6e150283cf46b2afaf7d79fedaca0dad

Tx prefix hash: c7a22da1759e61f03b76742f1af143bc6849c640c6e294876b8e1ba2104a5fdf
Tx public key: 8af18d105e0fa3b4f3a2cd17dbf37d4fb4d279a3d427eaf21f9dc5a157ec4155
Timestamp: 1580370458 Timestamp [UCT]: 2020-01-30 07:47:38 Age [y:d:h:m:s]: 05:045:04:56:26
Block: 54971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184163 RingCT/type: yes/0
Extra: 018af18d105e0fa3b4f3a2cd17dbf37d4fb4d279a3d427eaf21f9dc5a157ec4155021100000002391a8d0e000000000000000000

1 output(s) for total of 403.514442168000 dcy

stealth address amount amount idx
00: a8d2dc4756891ed01e120c1b211b345ab1a6e1fa6619fcf009a8ece0bce76ff7 403.514442168000 101637 of 0

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": 54981, "vin": [ { "gen": { "height": 54971 } } ], "vout": [ { "amount": 403514442168, "target": { "key": "a8d2dc4756891ed01e120c1b211b345ab1a6e1fa6619fcf009a8ece0bce76ff7" } } ], "extra": [ 1, 138, 241, 141, 16, 94, 15, 163, 180, 243, 162, 205, 23, 219, 243, 125, 79, 180, 210, 121, 163, 212, 39, 234, 242, 31, 157, 197, 161, 87, 236, 65, 85, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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