Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07308a289d1925bc859c956a7a9901a5bb23ba6603a6f82bd5b1812957e4b864

Tx prefix hash: 08c50e3115776623b5d7de12cbead51bad860bb0d1b694bd10092a9874a475ba
Tx public key: 9088a47a35e0c0aabe3aa00a8010592f1ce2d09dc02176a09563139fb8b9db3e
Timestamp: 1709137718 Timestamp [UCT]: 2024-02-28 16:28:38 Age [y:d:h:m:s]: 01:256:08:10:36
Block: 967510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441936 RingCT/type: yes/0
Extra: 019088a47a35e0c0aabe3aa00a8010592f1ce2d09dc02176a09563139fb8b9db3e0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 553ce1ef6e3044c66f8b25e7811d97abff418daa48bfbbb341fb237909953dac 0.600000000000 1427291 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": 967520, "vin": [ { "gen": { "height": 967510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "553ce1ef6e3044c66f8b25e7811d97abff418daa48bfbbb341fb237909953dac" } } ], "extra": [ 1, 144, 136, 164, 122, 53, 224, 192, 170, 190, 58, 160, 10, 128, 16, 89, 47, 28, 226, 208, 157, 192, 33, 118, 160, 149, 99, 19, 159, 184, 185, 219, 62, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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