Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bac7c32f0a7a912e0cd2e877645f81da4e145d2d616d4b73e47ad4be42af57a

Tx prefix hash: 4fe29cad7e0df3a8936828b45b793441b9027206f0ff0b32c87ec52cddf5a6e1
Tx public key: e61cdadff3005d4dbf0e2072f1de4c4fcc849661e4d24cdc94d310aed270bf5d
Timestamp: 1737356660 Timestamp [UCT]: 2025-01-20 07:04:20 Age [y:d:h:m:s]: 00:331:14:21:54
Block: 1201250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234588 RingCT/type: yes/0
Extra: 01e61cdadff3005d4dbf0e2072f1de4c4fcc849661e4d24cdc94d310aed270bf5d02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd3eb9461c6dfc75bccee5578334412f1d57529a3f955ac26995c0e4bae5635c 0.600000000000 1687899 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": 1201260, "vin": [ { "gen": { "height": 1201250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd3eb9461c6dfc75bccee5578334412f1d57529a3f955ac26995c0e4bae5635c" } } ], "extra": [ 1, 230, 28, 218, 223, 243, 0, 93, 77, 191, 14, 32, 114, 241, 222, 76, 79, 204, 132, 150, 97, 228, 210, 76, 220, 148, 211, 16, 174, 210, 112, 191, 93, 2, 17, 0, 0, 0, 11, 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