Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 287a372d1d64548f45cd198740cd7272d6d639a94d5f7fd4a07cd457e802f083

Tx prefix hash: 6f76ca31c300483392a4f9b4e0170a40f7a1769084b66ad28ff03fd12ce160f6
Tx public key: 4977a62f39f819ae936917bedec05492ae0e0ce5c7876e1c9a060f9e53436a22
Timestamp: 1746659996 Timestamp [UCT]: 2025-05-07 23:19:56 Age [y:d:h:m:s]: 00:269:13:14:15
Block: 1278054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190270 RingCT/type: yes/0
Extra: 014977a62f39f819ae936917bedec05492ae0e0ce5c7876e1c9a060f9e53436a220211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2e2a43fa2530df540c1e937f47fc77dbc19bf37a0cce6f32cfe0f94883f897b 0.600000000000 1765413 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": 1278064, "vin": [ { "gen": { "height": 1278054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2e2a43fa2530df540c1e937f47fc77dbc19bf37a0cce6f32cfe0f94883f897b" } } ], "extra": [ 1, 73, 119, 166, 47, 57, 248, 25, 174, 147, 105, 23, 190, 222, 192, 84, 146, 174, 14, 12, 229, 199, 135, 110, 28, 154, 6, 15, 158, 83, 67, 106, 34, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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