Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5d3fc6ab75b65c77a980ebcdff9a6321567b2481b61383d93fcf9eb38b4896a

Tx prefix hash: 52aceed3e527d5885c15441bacb70166d6ed7a8f21c332103190484bc2bf9b66
Tx public key: 4e482fc83b5d333908d76d98aa1401251f1fd89edab4b379e5ea83c840e64586
Timestamp: 1693339217 Timestamp [UCT]: 2023-08-29 20:00:17 Age [y:d:h:m:s]: 01:180:07:28:08
Block: 836698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389962 RingCT/type: yes/0
Extra: 014e482fc83b5d333908d76d98aa1401251f1fd89edab4b379e5ea83c840e6458602110000000775e3f0e9000000000000000000

1 output(s) for total of 1.036745770000 dcy

stealth address amount amount idx
00: c0711e1ccf5b2141a9b4776f4126ec5519cac5b38137a3cee7d2628a1360e8ef 1.036745770000 1289294 of 0

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": 836708, "vin": [ { "gen": { "height": 836698 } } ], "vout": [ { "amount": 1036745770, "target": { "key": "c0711e1ccf5b2141a9b4776f4126ec5519cac5b38137a3cee7d2628a1360e8ef" } } ], "extra": [ 1, 78, 72, 47, 200, 59, 93, 51, 57, 8, 215, 109, 152, 170, 20, 1, 37, 31, 31, 216, 158, 218, 180, 179, 121, 229, 234, 131, 200, 64, 230, 69, 134, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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