Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d8d53c8c24e4969cff6af49bf6ee2e3b49305666cdb51b63a95b690c654364e

Tx prefix hash: 427a06693711ae9f0e1d4832c5de3ac75d0aa71e23c79590447847bcf749b34d
Tx public key: 50f1a3c52173339726b065713523f7dd9f84e7c340d8fb1c86eb7411786f8429
Timestamp: 1724645322 Timestamp [UCT]: 2024-08-26 04:08:42 Age [y:d:h:m:s]: 00:294:22:15:40
Block: 1096065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210584 RingCT/type: yes/0
Extra: 0150f1a3c52173339726b065713523f7dd9f84e7c340d8fb1c86eb7411786f8429021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7402a91626ca2fb0fe21fc46a9cf9574ef9dcb1f9696637639a615571d726d7 0.600000000000 1571252 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": 1096075, "vin": [ { "gen": { "height": 1096065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7402a91626ca2fb0fe21fc46a9cf9574ef9dcb1f9696637639a615571d726d7" } } ], "extra": [ 1, 80, 241, 163, 197, 33, 115, 51, 151, 38, 176, 101, 113, 53, 35, 247, 221, 159, 132, 231, 195, 64, 216, 251, 28, 134, 235, 116, 17, 120, 111, 132, 41, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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