Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0673ba96df02bfc66015422f0b62c464d5a4f724b276bda956e9690f278ca94b

Tx prefix hash: 4fa812a0343902c217c13f407782c7a95bad608beb2aad7c584b6e4b7e6fd18e
Tx public key: dc31515d555de8325548a1da252f21eebd8e6f3be3d1ec62c8c823ba94917384
Timestamp: 1717853119 Timestamp [UCT]: 2024-06-08 13:25:19 Age [y:d:h:m:s]: 00:144:11:53:47
Block: 1039757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103412 RingCT/type: yes/0
Extra: 01dc31515d555de8325548a1da252f21eebd8e6f3be3d1ec62c8c823ba949173840211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f93f1fb1c620673fb4f670158cf476ea849cd9a74592e23aaf252b54afbb4c8 0.600000000000 1508412 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": 1039767, "vin": [ { "gen": { "height": 1039757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f93f1fb1c620673fb4f670158cf476ea849cd9a74592e23aaf252b54afbb4c8" } } ], "extra": [ 1, 220, 49, 81, 93, 85, 93, 232, 50, 85, 72, 161, 218, 37, 47, 33, 238, 189, 142, 111, 59, 227, 209, 236, 98, 200, 200, 35, 186, 148, 145, 115, 132, 2, 17, 0, 0, 0, 2, 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