Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24e74751dab0229504c0f69fcd3658d6ca488fc957ab31931a05a96107a65115

Tx prefix hash: a474603753e505a3a5a55fd05dfae87704ed7a381cb8ea16140e15f7d9fc95d4
Tx public key: 3c0ef8ef92e1fc0d933f4a6f740bd37bb3c4fad2bdc42fba4d3f76847caf3412
Timestamp: 1766214606 Timestamp [UCT]: 2025-12-20 07:10:06 Age [y:d:h:m:s]: 00:001:11:58:19
Block: 1437564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1064 RingCT/type: yes/0
Extra: 013c0ef8ef92e1fc0d933f4a6f740bd37bb3c4fad2bdc42fba4d3f76847caf34120211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 463f9161ee2efb151f3eece298d60e06b1c38ca290d41f7d716e3e19ebc2dbc9 0.600000000000 1926373 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": 1437574, "vin": [ { "gen": { "height": 1437564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "463f9161ee2efb151f3eece298d60e06b1c38ca290d41f7d716e3e19ebc2dbc9" } } ], "extra": [ 1, 60, 14, 248, 239, 146, 225, 252, 13, 147, 63, 74, 111, 116, 11, 211, 123, 179, 196, 250, 210, 189, 196, 47, 186, 77, 63, 118, 132, 124, 175, 52, 18, 2, 17, 0, 0, 0, 4, 123, 30, 81, 172, 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