Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24e429a64808afc26fcefa205a167b86cb26f16b5a23658aba708d3eb1d34497

Tx prefix hash: 7dc5f52ebd22d984a8d6cc4fb2d65cc556f47111c71ab263450993e9fa37e2b0
Tx public key: 8cf9c4798e0af1ff76b3f094b4941e420ce04f93a3bf6d22aa4885dc4cc7f135
Timestamp: 1761669260 Timestamp [UCT]: 2025-10-28 16:34:20 Age [y:d:h:m:s]: 00:012:03:06:33
Block: 1399902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8681 RingCT/type: yes/0
Extra: 018cf9c4798e0af1ff76b3f094b4941e420ce04f93a3bf6d22aa4885dc4cc7f1350211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5c80cdf76509ce97326b2c58600ba63e1b46a5f9ede07fa0e243f9403468614 0.600000000000 1888209 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": 1399912, "vin": [ { "gen": { "height": 1399902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5c80cdf76509ce97326b2c58600ba63e1b46a5f9ede07fa0e243f9403468614" } } ], "extra": [ 1, 140, 249, 196, 121, 142, 10, 241, 255, 118, 179, 240, 148, 180, 148, 30, 66, 12, 224, 79, 147, 163, 191, 109, 34, 170, 72, 133, 220, 76, 199, 241, 53, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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