Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1f758b7b058626b83dd5ab1a12dcaf4e52f68d2e304f31e88ae1d15c69d441f

Tx prefix hash: 3b04db5b2755a3095bc60f5d4e70ea0593d429d367ec6a37c0909fe23425c82a
Tx public key: 4ef72911f2a75453a939c08e400c25c5e142cc53ce1b7dfdf1fae34c401aaee1
Timestamp: 1732315399 Timestamp [UCT]: 2024-11-22 22:43:19 Age [y:d:h:m:s]: 00:140:09:04:42
Block: 1159566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100142 RingCT/type: yes/0
Extra: 014ef72911f2a75453a939c08e400c25c5e142cc53ce1b7dfdf1fae34c401aaee102110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc4284c9ba0dadab266f2c94a7f2f4b422401992187206341a73a7edcb6c855c 0.600000000000 1645205 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": 1159576, "vin": [ { "gen": { "height": 1159566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc4284c9ba0dadab266f2c94a7f2f4b422401992187206341a73a7edcb6c855c" } } ], "extra": [ 1, 78, 247, 41, 17, 242, 167, 84, 83, 169, 57, 192, 142, 64, 12, 37, 197, 225, 66, 204, 83, 206, 27, 125, 253, 241, 250, 227, 76, 64, 26, 174, 225, 2, 17, 0, 0, 0, 10, 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