Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 222fe99289503bd90c584e974887096a21e0498ea4ff2a94ba4ec31c26ce0a8b

Tx prefix hash: 59e3a4ddee1ffd6aa419266b08021767177ddbb1ca3102b9201417b6fc176e59
Tx public key: 7e853a6a5a70454e5a67f99189a3b444b68121b90527797ddd19a97a0b51b369
Timestamp: 1725309465 Timestamp [UCT]: 2024-09-02 20:37:45 Age [y:d:h:m:s]: 00:227:21:22:11
Block: 1101574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162732 RingCT/type: yes/0
Extra: 017e853a6a5a70454e5a67f99189a3b444b68121b90527797ddd19a97a0b51b369021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c4b4cf6d7d5ab45100c18625c07ed1f8a32438c8f5f259724e084ac51ff5ef1 0.600000000000 1577677 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": 1101584, "vin": [ { "gen": { "height": 1101574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c4b4cf6d7d5ab45100c18625c07ed1f8a32438c8f5f259724e084ac51ff5ef1" } } ], "extra": [ 1, 126, 133, 58, 106, 90, 112, 69, 78, 90, 103, 249, 145, 137, 163, 180, 68, 182, 129, 33, 185, 5, 39, 121, 125, 221, 25, 169, 122, 11, 81, 179, 105, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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