Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32efb7025953707679dc967d03f84ec5dfdf9e9b7477e8e48ca1303efa7dd092

Tx prefix hash: 3030a4d373f85455553aa4fd76322839c8870e77ee7cf519b9e5985368a382f3
Tx public key: f64dadaa5ec36525c9fa25335cc090fc77e1c5c530dc15c63f7f66b0ca24f929
Timestamp: 1713895816 Timestamp [UCT]: 2024-04-23 18:10:16 Age [y:d:h:m:s]: 01:055:06:33:44
Block: 1006948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300354 RingCT/type: yes/0
Extra: 01f64dadaa5ec36525c9fa25335cc090fc77e1c5c530dc15c63f7f66b0ca24f92902110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6172658a83df2fc9594f78a9c453a785ade91bce678706e4ec342581c300512 0.600000000000 1468142 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": 1006958, "vin": [ { "gen": { "height": 1006948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6172658a83df2fc9594f78a9c453a785ade91bce678706e4ec342581c300512" } } ], "extra": [ 1, 246, 77, 173, 170, 94, 195, 101, 37, 201, 250, 37, 51, 92, 192, 144, 252, 119, 225, 197, 197, 48, 220, 21, 198, 63, 127, 102, 176, 202, 36, 249, 41, 2, 17, 0, 0, 0, 14, 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