Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 073f0040fbdceebe4013d2d06df6c6a73fec749489d0b4913718d166a7969fef

Tx prefix hash: 7528ac029ef20992df32156f6981fdd6e497b4128d49cc5f494f6dcdfe5e5cd7
Tx public key: ca8b33d9c77f459bbe57ac5d088ee76f5c76b31610f4e3dcfc9e900a715abec0
Timestamp: 1726530103 Timestamp [UCT]: 2024-09-16 23:41:43 Age [y:d:h:m:s]: 00:276:04:31:37
Block: 1111686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197131 RingCT/type: yes/0
Extra: 01ca8b33d9c77f459bbe57ac5d088ee76f5c76b31610f4e3dcfc9e900a715abec002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10966708bf88382dc79868596b42debef35ae6f3e67a44c5f8c7bde9675c5fb0 0.600000000000 1590735 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": 1111696, "vin": [ { "gen": { "height": 1111686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10966708bf88382dc79868596b42debef35ae6f3e67a44c5f8c7bde9675c5fb0" } } ], "extra": [ 1, 202, 139, 51, 217, 199, 127, 69, 155, 190, 87, 172, 93, 8, 142, 231, 111, 92, 118, 179, 22, 16, 244, 227, 220, 252, 158, 144, 10, 113, 90, 190, 192, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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