Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79ffef7a866447765ace8eb69384744d118a6fc7019c25f27276c4f11c09671e

Tx prefix hash: f4aa85b4dcbf817997a8da4738c227fcc899bd970a00d7776fab28da324bc0e3
Tx public key: 1f4eef718db3cf21e8d73c4ee64c14fdadad91dc8838af9fd695c0fb281f27d1
Timestamp: 1761070296 Timestamp [UCT]: 2025-10-21 18:11:36 Age [y:d:h:m:s]: 00:030:00:46:44
Block: 1394944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21486 RingCT/type: yes/0
Extra: 011f4eef718db3cf21e8d73c4ee64c14fdadad91dc8838af9fd695c0fb281f27d1021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3f5551df1889d71088436328a66f3c99e6f507f3c63118f12a5d1ea50d26e54 0.600000000000 1883219 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": 1394954, "vin": [ { "gen": { "height": 1394944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f5551df1889d71088436328a66f3c99e6f507f3c63118f12a5d1ea50d26e54" } } ], "extra": [ 1, 31, 78, 239, 113, 141, 179, 207, 33, 232, 215, 60, 78, 230, 76, 20, 253, 173, 173, 145, 220, 136, 56, 175, 159, 214, 149, 192, 251, 40, 31, 39, 209, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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