Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f84a6e561b6a7fffa523ba6234510e90e2f45842da9c6ef903f27150217d0ea9

Tx prefix hash: 67c7ce8a91c8241fd21b418d072732974db07443b7da5aa1ffe7055df5ed3f01
Tx public key: 5a92b7041aa7734960a8c890e75fe7fab1239731dd3a5ed12dfe8b6868c1ad0c
Timestamp: 1725781835 Timestamp [UCT]: 2024-09-08 07:50:35 Age [y:d:h:m:s]: 00:207:17:41:59
Block: 1105491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148302 RingCT/type: yes/0
Extra: 015a92b7041aa7734960a8c890e75fe7fab1239731dd3a5ed12dfe8b6868c1ad0c021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c917e576a70f89050a010ffce1d2bca49ff1b400678c64eaf743015367a49379 0.600000000000 1582838 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": 1105501, "vin": [ { "gen": { "height": 1105491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c917e576a70f89050a010ffce1d2bca49ff1b400678c64eaf743015367a49379" } } ], "extra": [ 1, 90, 146, 183, 4, 26, 167, 115, 73, 96, 168, 200, 144, 231, 95, 231, 250, 177, 35, 151, 49, 221, 58, 94, 209, 45, 254, 139, 104, 104, 193, 173, 12, 2, 17, 0, 0, 0, 8, 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