Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c16644f88bdaef9ffff0f1b80f41909d5be0cbee869d556c20c9ca0cd0950bbe

Tx prefix hash: 49331155be11f1db5532ab4dd16be3ff8372e5cdaa43f53a2da2659752dab446
Tx public key: 0965400d87cf42948a04a2e8c4521404eb8a0e713b3a53c06b6d9accf5bf7c6c
Timestamp: 1737894684 Timestamp [UCT]: 2025-01-26 12:31:24 Age [y:d:h:m:s]: 00:141:20:51:42
Block: 1205712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101143 RingCT/type: yes/0
Extra: 010965400d87cf42948a04a2e8c4521404eb8a0e713b3a53c06b6d9accf5bf7c6c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c270804b07617d38ae738c71f70014813a3a5d3cb1aad8f851eb25ad7da0be9 0.600000000000 1692411 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": 1205722, "vin": [ { "gen": { "height": 1205712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c270804b07617d38ae738c71f70014813a3a5d3cb1aad8f851eb25ad7da0be9" } } ], "extra": [ 1, 9, 101, 64, 13, 135, 207, 66, 148, 138, 4, 162, 232, 196, 82, 20, 4, 235, 138, 14, 113, 59, 58, 83, 192, 107, 109, 154, 204, 245, 191, 124, 108, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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