Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d6cf9f440e7b869b918055051d7c5fdb19fdc571c15ce63d46e393301bdeb52

Tx prefix hash: 12ee8470b6cb96b0fb94bb5a592c424a511ed84d1e658cd853707476404388b3
Tx public key: ea3e4cc51623ddf8abd717a859371bb4b4ec188039583b31771c7a1f3c53bfe5
Timestamp: 1707767742 Timestamp [UCT]: 2024-02-12 19:55:42 Age [y:d:h:m:s]: 01:056:22:41:41
Block: 956141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301737 RingCT/type: yes/0
Extra: 01ea3e4cc51623ddf8abd717a859371bb4b4ec188039583b31771c7a1f3c53bfe502110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee863e787a75c2fb66b7c2daf0398c1a079ff2c66454e8834a4deeb7f76ad4a7 0.600000000000 1415443 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": 956151, "vin": [ { "gen": { "height": 956141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee863e787a75c2fb66b7c2daf0398c1a079ff2c66454e8834a4deeb7f76ad4a7" } } ], "extra": [ 1, 234, 62, 76, 197, 22, 35, 221, 248, 171, 215, 23, 168, 89, 55, 27, 180, 180, 236, 24, 128, 57, 88, 59, 49, 119, 28, 122, 31, 60, 83, 191, 229, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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