Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1deb99385a949b92a01e34de1169c4eb7b2140fbcff46fcce4f06edf0753f19

Tx prefix hash: 16e5a8368ab87b529179736cff377fe428ffe3c75fdfbe595bd7ace3ce065204
Tx public key: 3ae4aeabb60c3228a0dd91f965ed0852a718e81a8beef149d0e4714c6d5e5cfd
Timestamp: 1704231385 Timestamp [UCT]: 2024-01-02 21:36:25 Age [y:d:h:m:s]: 01:089:12:51:56
Block: 926816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325095 RingCT/type: yes/0
Extra: 013ae4aeabb60c3228a0dd91f965ed0852a718e81a8beef149d0e4714c6d5e5cfd0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c68eea3313d0f5e1e01241ca464082226aa570e6bae641500c10f25218a821b8 0.600000000000 1384614 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": 926826, "vin": [ { "gen": { "height": 926816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c68eea3313d0f5e1e01241ca464082226aa570e6bae641500c10f25218a821b8" } } ], "extra": [ 1, 58, 228, 174, 171, 182, 12, 50, 40, 160, 221, 145, 249, 101, 237, 8, 82, 167, 24, 232, 26, 139, 238, 241, 73, 208, 228, 113, 76, 109, 94, 92, 253, 2, 17, 0, 0, 0, 2, 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