Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6b94ec8231db1c8f71d2f171d3a80f314c9f147b8b85b82d6be63689147bbca

Tx prefix hash: fe6da49c7e6815c6438bb474c33df2e07865c711a018a80179373c24d5ca36ae
Tx public key: 0dd936052bbb6739bfe43523a1e6bdc13e56a42fd6d65b3040fa1d0900629bc3
Timestamp: 1726242267 Timestamp [UCT]: 2024-09-13 15:44:27 Age [y:d:h:m:s]: 01:068:08:53:10
Block: 1109305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307282 RingCT/type: yes/0
Extra: 010dd936052bbb6739bfe43523a1e6bdc13e56a42fd6d65b3040fa1d0900629bc302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee9cf94b70f36cf192786117ea1a0689f36c3e53ac122133c523c787e3a1b7b7 0.600000000000 1587510 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": 1109315, "vin": [ { "gen": { "height": 1109305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee9cf94b70f36cf192786117ea1a0689f36c3e53ac122133c523c787e3a1b7b7" } } ], "extra": [ 1, 13, 217, 54, 5, 43, 187, 103, 57, 191, 228, 53, 35, 161, 230, 189, 193, 62, 86, 164, 47, 214, 214, 91, 48, 64, 250, 29, 9, 0, 98, 155, 195, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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