Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a916be2da8335551924695dbd03b87a4d6b39a98f16191e4cb80a2b5b76a297

Tx prefix hash: 727a1670e1b79d715673c1c27238b0093196a16cbb05d0b51fde080df3781945
Tx public key: 99f9de17cc8599fd9f10e972c446cd554323e9176d093edf0001178692569273
Timestamp: 1581571282 Timestamp [UCT]: 2020-02-13 05:21:22 Age [y:d:h:m:s]: 04:320:13:41:57
Block: 63956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121243 RingCT/type: yes/0
Extra: 0199f9de17cc8599fd9f10e972c446cd554323e9176d093edf0001178692569273021100000002c71d3ff9000000000000000000

1 output(s) for total of 376.780167745000 dcy

stealth address amount amount idx
00: 63f7c6a399f560673c3f8e54c5d1b1e57aac29498a75597c26cec8df3c22b16d 376.780167745000 117869 of 0

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": 63966, "vin": [ { "gen": { "height": 63956 } } ], "vout": [ { "amount": 376780167745, "target": { "key": "63f7c6a399f560673c3f8e54c5d1b1e57aac29498a75597c26cec8df3c22b16d" } } ], "extra": [ 1, 153, 249, 222, 23, 204, 133, 153, 253, 159, 16, 233, 114, 196, 70, 205, 85, 67, 35, 233, 23, 109, 9, 62, 223, 0, 1, 23, 134, 146, 86, 146, 115, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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