Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4ccb56dcf37cd2c5ba14f61228308e67292ca31d6c31db6f852cdeae17be59e

Tx prefix hash: b341b41a4df5b3d871c94d4ae0330c833ced7bbe0691584b834f271a0cc5534c
Tx public key: d508bcd90a59d764276ed3ae3e5d0e9cf5db4daebaba8d790165dab57a34505d
Timestamp: 1696841304 Timestamp [UCT]: 2023-10-09 08:48:24 Age [y:d:h:m:s]: 01:177:04:18:20
Block: 865769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387654 RingCT/type: yes/0
Extra: 01d508bcd90a59d764276ed3ae3e5d0e9cf5db4daebaba8d790165dab57a34505d02110000000433af99f4000000000000000000

1 output(s) for total of 0.830515876000 dcy

stealth address amount amount idx
00: 3eb495bd34aa278cac544d1beaf70118ddb38acd8a2ce5bc567b97497f9430db 0.830515876000 1320315 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": 865779, "vin": [ { "gen": { "height": 865769 } } ], "vout": [ { "amount": 830515876, "target": { "key": "3eb495bd34aa278cac544d1beaf70118ddb38acd8a2ce5bc567b97497f9430db" } } ], "extra": [ 1, 213, 8, 188, 217, 10, 89, 215, 100, 39, 110, 211, 174, 62, 93, 14, 156, 245, 219, 77, 174, 186, 186, 141, 121, 1, 101, 218, 181, 122, 52, 80, 93, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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