Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f18e562d6baec6e90123fbe4e1e6366e5b8db60315814ce599e8ce1a4e7287cf

Tx prefix hash: bf199e99f86bd7957cbaee0e64cac192f7454fc5ef3868dcfe31a4f0ce5ed092
Tx public key: 3dd144f99c1ea242c4636b6a9107e8b9d355acfc5fc7c6582317352ea1f2a36f
Timestamp: 1759650723 Timestamp [UCT]: 2025-10-05 07:52:03 Age [y:d:h:m:s]: 00:002:23:04:43
Block: 1383159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2119 RingCT/type: yes/0
Extra: 013dd144f99c1ea242c4636b6a9107e8b9d355acfc5fc7c6582317352ea1f2a36f02110000000497baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1475ab4066f47c14ad5826f8df6ae2cf26d0ef3d844a2ec7e7cf5777bb5ef43 0.600000000000 1871304 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": 1383169, "vin": [ { "gen": { "height": 1383159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1475ab4066f47c14ad5826f8df6ae2cf26d0ef3d844a2ec7e7cf5777bb5ef43" } } ], "extra": [ 1, 61, 209, 68, 249, 156, 30, 162, 66, 196, 99, 107, 106, 145, 7, 232, 185, 211, 85, 172, 252, 95, 199, 198, 88, 35, 23, 53, 46, 161, 242, 163, 111, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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