Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20ddade6a32da0ac34f3d6baf6ef2d25fde71ae40bb0f4967efee44bd7e537a1

Tx prefix hash: dad3266eeacb8053185d1479d0c501feffcbfb8cd951286c4968b868662c4ac3
Tx public key: 4e801fd1c68aca37318179d2198be8c7407e7f2e4d29e8e99228a871dd210475
Timestamp: 1758718022 Timestamp [UCT]: 2025-09-24 12:47:02 Age [y:d:h:m:s]: 00:090:14:10:15
Block: 1375433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64856 RingCT/type: yes/0
Extra: 014e801fd1c68aca37318179d2198be8c7407e7f2e4d29e8e99228a871dd210475021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1e4163467310d7ddb42e2dba61ab2f74c6fd4873e00fc1d96f70216da49a4e7 0.600000000000 1863518 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": 1375443, "vin": [ { "gen": { "height": 1375433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1e4163467310d7ddb42e2dba61ab2f74c6fd4873e00fc1d96f70216da49a4e7" } } ], "extra": [ 1, 78, 128, 31, 209, 198, 138, 202, 55, 49, 129, 121, 210, 25, 139, 232, 199, 64, 126, 127, 46, 77, 41, 232, 233, 146, 40, 168, 113, 221, 33, 4, 117, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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