Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9402d9c558d6327bea536eb7df842f521975c05bbaa55aabbd9abf8c8571baa

Tx prefix hash: 6a7d3a1e35c89974510819c544c7061a5bfefd9a84c8de48a33fc4396c7a892f
Tx public key: 5dd7854f7b8e2357fd8f256bac0925d80cb2aeab27b3a458035387c5bdb34c78
Timestamp: 1707026816 Timestamp [UCT]: 2024-02-04 06:06:56 Age [y:d:h:m:s]: 01:024:16:49:05
Block: 949985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278689 RingCT/type: yes/0
Extra: 015dd7854f7b8e2357fd8f256bac0925d80cb2aeab27b3a458035387c5bdb34c7802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a054843b93aa8137d1b5c51db3deeffd9548c451351d84c01d228a0145347b9d 0.600000000000 1408523 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": 949995, "vin": [ { "gen": { "height": 949985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a054843b93aa8137d1b5c51db3deeffd9548c451351d84c01d228a0145347b9d" } } ], "extra": [ 1, 93, 215, 133, 79, 123, 142, 35, 87, 253, 143, 37, 107, 172, 9, 37, 216, 12, 178, 174, 171, 39, 179, 164, 88, 3, 83, 135, 197, 189, 179, 76, 120, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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