Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 536bf0c68ed7eee1c10cb58a20d5a4f330c83011cea5d1ee4cd6de10c5c754b3

Tx prefix hash: 6419c42639420bc3ae34f8fbc89bc0a3c094cdb3ee85ad32b73582878437e8eb
Tx public key: 2169c356eacb7817aa819c6c7900fe073b49d1d8ac19325b73641aeccdc988fb
Timestamp: 1720953178 Timestamp [UCT]: 2024-07-14 10:32:58 Age [y:d:h:m:s]: 00:274:03:12:06
Block: 1065473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195841 RingCT/type: yes/0
Extra: 012169c356eacb7817aa819c6c7900fe073b49d1d8ac19325b73641aeccdc988fb02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d72f3a403f1ca7b5c96fdb85b256c2bea544f3d99878699c8ca016a8ed9312e 0.600000000000 1536020 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": 1065483, "vin": [ { "gen": { "height": 1065473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d72f3a403f1ca7b5c96fdb85b256c2bea544f3d99878699c8ca016a8ed9312e" } } ], "extra": [ 1, 33, 105, 195, 86, 234, 203, 120, 23, 170, 129, 156, 108, 121, 0, 254, 7, 59, 73, 209, 216, 172, 25, 50, 91, 115, 100, 26, 236, 205, 201, 136, 251, 2, 17, 0, 0, 0, 7, 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