Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dfc585a2228cef13de8d74de766cdf57b2b8061a0630becde7d7ebbf9ede67f

Tx prefix hash: d441e1b212b01552fcf5e7c787099b9624c5558e8a4bba7cb3ad2badbe344e52
Tx public key: a7ba6d1d28b12a20a42b8a90e9d502da451bb06e02cd2770371f29e34547abd1
Timestamp: 1724834905 Timestamp [UCT]: 2024-08-28 08:48:25 Age [y:d:h:m:s]: 00:217:07:32:25
Block: 1097634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155175 RingCT/type: yes/0
Extra: 01a7ba6d1d28b12a20a42b8a90e9d502da451bb06e02cd2770371f29e34547abd1021100000006e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: afc24278797207ed95c86f4f43b7c8e2b700f7637db16d94addbfdf65bbce35e 0.608000000000 1573061 of 0

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": 1097644, "vin": [ { "gen": { "height": 1097634 } } ], "vout": [ { "amount": 608000000, "target": { "key": "afc24278797207ed95c86f4f43b7c8e2b700f7637db16d94addbfdf65bbce35e" } } ], "extra": [ 1, 167, 186, 109, 29, 40, 177, 42, 32, 164, 43, 138, 144, 233, 213, 2, 218, 69, 27, 176, 110, 2, 205, 39, 112, 55, 31, 41, 227, 69, 71, 171, 209, 2, 17, 0, 0, 0, 6, 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