Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffce16934f6d86f07e17f227fbbd4a0e0c410d0772540fb062bb8898336967e5

Tx prefix hash: ab40c4b96282db5b83a8a12c4e715f8705f34362198bcdd2015f70e77c5f6a01
Tx public key: e0ef2775f3bdb1ccd9b1ec37c56e550f78acf4a0d99ff91179e5015588ad72fc
Timestamp: 1763184970 Timestamp [UCT]: 2025-11-15 05:36:10 Age [y:d:h:m:s]: 00:076:22:40:54
Block: 1412456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54912 RingCT/type: yes/0
Extra: 01e0ef2775f3bdb1ccd9b1ec37c56e550f78acf4a0d99ff91179e5015588ad72fc02110000000601491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3273642c0b76275f96db2c6a8aa68e2e3eef9ef22c68030ae0e308a080ecd959 0.600000000000 1900925 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": 1412466, "vin": [ { "gen": { "height": 1412456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3273642c0b76275f96db2c6a8aa68e2e3eef9ef22c68030ae0e308a080ecd959" } } ], "extra": [ 1, 224, 239, 39, 117, 243, 189, 177, 204, 217, 177, 236, 55, 197, 110, 85, 15, 120, 172, 244, 160, 217, 159, 249, 17, 121, 229, 1, 85, 136, 173, 114, 252, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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