Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa7aeea5d7682fdf0452607ffb715858bb8bf6e3f0d91828bcc338d9f6d0621f

Tx prefix hash: eb40ab8167e2620cbc2556bf2a999292994ef69f7fec624d1cf3c58de4c6c7e0
Tx public key: 3eb0aa893bebd0afae8672d6c4ccf7aa8ff69255497f32efabdbee6bc887dcd0
Timestamp: 1732034133 Timestamp [UCT]: 2024-11-19 16:35:33 Age [y:d:h:m:s]: 00:140:18:19:40
Block: 1157239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100418 RingCT/type: yes/0
Extra: 013eb0aa893bebd0afae8672d6c4ccf7aa8ff69255497f32efabdbee6bc887dcd00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0476f542e282d489757b70973f36a3bbbbd67a2fadfc6c88c52ca6822e8e1ca 0.600000000000 1642862 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": 1157249, "vin": [ { "gen": { "height": 1157239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0476f542e282d489757b70973f36a3bbbbd67a2fadfc6c88c52ca6822e8e1ca" } } ], "extra": [ 1, 62, 176, 170, 137, 59, 235, 208, 175, 174, 134, 114, 214, 196, 204, 247, 170, 143, 246, 146, 85, 73, 127, 50, 239, 171, 219, 238, 107, 200, 135, 220, 208, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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