Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 235f25d43fc27c8c77288967bd5c53051f909e10c5b069506364e24425df5f24

Tx prefix hash: 609c11b3a3004d872c4a923a5884a34d98e1ab9e2f8eff2cbeebc20e7de5a612
Tx public key: 7a3b2755bbd390ce149db04e72304f1fc7d51b12058917736f14d55f87135bfa
Timestamp: 1723722161 Timestamp [UCT]: 2024-08-15 11:42:41 Age [y:d:h:m:s]: 00:287:06:20:01
Block: 1088419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205221 RingCT/type: yes/0
Extra: 017a3b2755bbd390ce149db04e72304f1fc7d51b12058917736f14d55f87135bfa021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b80b7fc77cac9a62b1ad0e489844a00b8ead8553f575bda32b43f29a7b7a243e 0.600000000000 1563036 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": 1088429, "vin": [ { "gen": { "height": 1088419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b80b7fc77cac9a62b1ad0e489844a00b8ead8553f575bda32b43f29a7b7a243e" } } ], "extra": [ 1, 122, 59, 39, 85, 187, 211, 144, 206, 20, 157, 176, 78, 114, 48, 79, 31, 199, 213, 27, 18, 5, 137, 23, 115, 111, 20, 213, 95, 135, 19, 91, 250, 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