Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 107deb8f617ce8556d2e67803433fd65f30f96ee0340530ae26c6c4bd688d833

Tx prefix hash: 940e88730a478758268fbf116f94334c1b814287c496182eca9a620a8665b47e
Tx public key: c7b65b0e19b0cb7cc9a99b45fa7ab945d06eec823e5e49d19c25397815888c81
Timestamp: 1712791889 Timestamp [UCT]: 2024-04-10 23:31:29 Age [y:d:h:m:s]: 01:041:11:42:48
Block: 997770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290663 RingCT/type: yes/0
Extra: 01c7b65b0e19b0cb7cc9a99b45fa7ab945d06eec823e5e49d19c25397815888c8102110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96a8cff1b1df2ece9d667fab68ce65961ca7fd19ab1caae72c4073fcc31805c3 0.600000000000 1458204 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": 997780, "vin": [ { "gen": { "height": 997770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96a8cff1b1df2ece9d667fab68ce65961ca7fd19ab1caae72c4073fcc31805c3" } } ], "extra": [ 1, 199, 182, 91, 14, 25, 176, 203, 124, 201, 169, 155, 69, 250, 122, 185, 69, 208, 110, 236, 130, 62, 94, 73, 209, 156, 37, 57, 120, 21, 136, 140, 129, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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