Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e330031ba580a52a2fb097e633944865c8843879b71f0e6e5078b29dfd1c558

Tx prefix hash: 51e73309b753ede44baef1b37213251a9f0a9d88d07b85cbaf3242ea89e2e62d
Tx public key: 7b8a838da9de1da3c7fc66b7352f9a15557e4cfe55678a360ff84f1aa0d9a219
Timestamp: 1721861317 Timestamp [UCT]: 2024-07-24 22:48:37 Age [y:d:h:m:s]: 00:247:05:40:34
Block: 1072982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176609 RingCT/type: yes/0
Extra: 017b8a838da9de1da3c7fc66b7352f9a15557e4cfe55678a360ff84f1aa0d9a219021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 236ff94930fb1a3a8571bb5e58008071920764d9a3850ecda37928168eccff56 0.600000000000 1545479 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": 1072992, "vin": [ { "gen": { "height": 1072982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "236ff94930fb1a3a8571bb5e58008071920764d9a3850ecda37928168eccff56" } } ], "extra": [ 1, 123, 138, 131, 141, 169, 222, 29, 163, 199, 252, 102, 183, 53, 47, 154, 21, 85, 126, 76, 254, 85, 103, 138, 54, 15, 248, 79, 26, 160, 217, 162, 25, 2, 17, 0, 0, 0, 4, 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