Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f16297a740bebceb8853bbb5f2af4d0ec5a1606b1133a759f53b395eb64e5239

Tx prefix hash: e9a59f0d445f6fea42f4a2d19ad60f9272fc3edc6db54e3a36d42843fb1892cf
Tx public key: 0bf7cb85220c5f2905601a839241a3c0eaaac939b817244ff37ffe00e0a87a42
Timestamp: 1719250376 Timestamp [UCT]: 2024-06-24 17:32:56 Age [y:d:h:m:s]: 00:267:00:27:42
Block: 1051326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190819 RingCT/type: yes/0
Extra: 010bf7cb85220c5f2905601a839241a3c0eaaac939b817244ff37ffe00e0a87a420211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56efad5d344f5afb5f24cccb70028f7d6f7607d8839faffcfdf7db2f75dd5229 0.600000000000 1521637 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": 1051336, "vin": [ { "gen": { "height": 1051326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56efad5d344f5afb5f24cccb70028f7d6f7607d8839faffcfdf7db2f75dd5229" } } ], "extra": [ 1, 11, 247, 203, 133, 34, 12, 95, 41, 5, 96, 26, 131, 146, 65, 163, 192, 234, 170, 201, 57, 184, 23, 36, 79, 243, 127, 254, 0, 224, 168, 122, 66, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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