Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf01ede481d1f4a5f70c945b0154d724a99c7bfa9aba6945f4703c641595d1ae

Tx prefix hash: f5868c7322e4b7b8e6e77b8f487625e83f0c46fa4a807697eaa56bc10d69bac0
Tx public key: b71304d3ba6ad51bdb1357918bd9d5ac01eb1c1fd75c4eecdc591bc51b8bf9de
Timestamp: 1736367436 Timestamp [UCT]: 2025-01-08 20:17:16 Age [y:d:h:m:s]: 00:115:01:40:45
Block: 1193111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82044 RingCT/type: yes/0
Extra: 01b71304d3ba6ad51bdb1357918bd9d5ac01eb1c1fd75c4eecdc591bc51b8bf9de021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 410eb67eff9bc18132dfbfeee208f4ab253cc7f863dfde06e191880455803a31 0.600000000000 1679670 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": 1193121, "vin": [ { "gen": { "height": 1193111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "410eb67eff9bc18132dfbfeee208f4ab253cc7f863dfde06e191880455803a31" } } ], "extra": [ 1, 183, 19, 4, 211, 186, 106, 213, 27, 219, 19, 87, 145, 139, 217, 213, 172, 1, 235, 28, 31, 215, 92, 78, 236, 220, 89, 27, 197, 27, 139, 249, 222, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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