Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f06893606bf3f191fb452dbf979b8ad86b07c68371e69ac7cdd62a159c46c07b

Tx prefix hash: 3afb4685506728873c51c71206ba909022bf7f247492c70f3546b8ee6e7eed8b
Tx public key: 038bdbe70eb7f88f85627cb9cf7a3d4cacfa836c7a0463b655cf257b74f5ecbf
Timestamp: 1762719582 Timestamp [UCT]: 2025-11-09 20:19:42 Age [y:d:h:m:s]: 00:058:15:49:15
Block: 1408605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42002 RingCT/type: yes/0
Extra: 01038bdbe70eb7f88f85627cb9cf7a3d4cacfa836c7a0463b655cf257b74f5ecbf021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd789d04e4746a1dfaf1e4ad993483566a2f73c4db9ed6d63f1f98d3fcdea4ae 0.600000000000 1897036 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": 1408615, "vin": [ { "gen": { "height": 1408605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd789d04e4746a1dfaf1e4ad993483566a2f73c4db9ed6d63f1f98d3fcdea4ae" } } ], "extra": [ 1, 3, 139, 219, 231, 14, 183, 248, 143, 133, 98, 124, 185, 207, 122, 61, 76, 172, 250, 131, 108, 122, 4, 99, 182, 85, 207, 37, 123, 116, 245, 236, 191, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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