Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6551361295f501b86891e1affbc2228427d088397ed7e59b97a457120b74dcc4

Tx prefix hash: 802b01eaf2bb911654b42d757f4889fc00a715236de1fe532c2bcbcf9a8aa893
Tx public key: eb5c48e683eadd159d4af6403d47696b8eaaf8d91f9cb1d0deab58dabb24c237
Timestamp: 1707951205 Timestamp [UCT]: 2024-02-14 22:53:25 Age [y:d:h:m:s]: 01:083:07:06:59
Block: 957655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320597 RingCT/type: yes/0
Extra: 01eb5c48e683eadd159d4af6403d47696b8eaaf8d91f9cb1d0deab58dabb24c23702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 522b8171452ffa89c412e3a94ab99eaae595df200e21f1fb26f35c7f5e09042c 0.600000000000 1416975 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": 957665, "vin": [ { "gen": { "height": 957655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "522b8171452ffa89c412e3a94ab99eaae595df200e21f1fb26f35c7f5e09042c" } } ], "extra": [ 1, 235, 92, 72, 230, 131, 234, 221, 21, 157, 74, 246, 64, 61, 71, 105, 107, 142, 170, 248, 217, 31, 156, 177, 208, 222, 171, 88, 218, 187, 36, 194, 55, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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