Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0665564e7e720881691f1d1b1aec73dfdbdfdcf84deed120ae318f25495f46

Tx prefix hash: b505c11d39ff3b1000b80ec1c0b34a81d9b60f714fe7b53138d595f6cb4f0442
Tx public key: 0fec98fc22ad2cfb3041305f22a0ca5f95a9f35583864c4b425f5837a30b6977
Timestamp: 1720743478 Timestamp [UCT]: 2024-07-12 00:17:58 Age [y:d:h:m:s]: 00:225:11:46:16
Block: 1063727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161038 RingCT/type: yes/0
Extra: 010fec98fc22ad2cfb3041305f22a0ca5f95a9f35583864c4b425f5837a30b697702110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55e3f604f8d1b7d5f2a06cb13e0cceb04edd9b11be642d3d96202834725b596f 0.600000000000 1534244 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": 1063737, "vin": [ { "gen": { "height": 1063727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55e3f604f8d1b7d5f2a06cb13e0cceb04edd9b11be642d3d96202834725b596f" } } ], "extra": [ 1, 15, 236, 152, 252, 34, 173, 44, 251, 48, 65, 48, 95, 34, 160, 202, 95, 149, 169, 243, 85, 131, 134, 76, 75, 66, 95, 88, 55, 163, 11, 105, 119, 2, 17, 0, 0, 0, 9, 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