Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0065a40821777b9af1937a97a468cd15f7be53e22fec3d7e23ef560f4ca6ff68

Tx prefix hash: a49878ea378118cc9d37db606b0db828e678a886251556a4a68bf3dfd6273a1a
Tx public key: 9ed36634184e105f1de58a4cf8f40df8c91c763b86824ef4c4797a0fcb49a08d
Timestamp: 1665688270 Timestamp [UCT]: 2022-10-13 19:11:10 Age [y:d:h:m:s]: 03:111:21:09:02
Block: 608344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 860100 RingCT/type: yes/0
Extra: 019ed36634184e105f1de58a4cf8f40df8c91c763b86824ef4c4797a0fcb49a08d02110000000475e3f0e9000000000000000000

1 output(s) for total of 5.919756458000 dcy

stealth address amount amount idx
00: b46fa4b484c51c6c1961530a7d4e771073ad9f3e9969d25776a6e81adeae0cc6 5.919756458000 1045028 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": 608354, "vin": [ { "gen": { "height": 608344 } } ], "vout": [ { "amount": 5919756458, "target": { "key": "b46fa4b484c51c6c1961530a7d4e771073ad9f3e9969d25776a6e81adeae0cc6" } } ], "extra": [ 1, 158, 211, 102, 52, 24, 78, 16, 95, 29, 229, 138, 76, 248, 244, 13, 248, 201, 28, 118, 59, 134, 130, 78, 244, 196, 121, 122, 15, 203, 73, 160, 141, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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