Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beffa73bc5b925c0fa57e21439c8f9a57f2dbcbda861c5eb367d49f19c6ca3af

Tx prefix hash: dc270b26d5815e71fa8970e24623e5faf927520f83659ca3ca159ba5d7d5a034
Tx public key: 132e33c2cf24fe00fcc1d687f4752c82a5b8c49cdfe40450a90cd021f48aef0f
Timestamp: 1707651337 Timestamp [UCT]: 2024-02-11 11:35:37 Age [y:d:h:m:s]: 01:266:19:30:22
Block: 955171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449454 RingCT/type: yes/0
Extra: 01132e33c2cf24fe00fcc1d687f4752c82a5b8c49cdfe40450a90cd021f48aef0f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0de4736980908992595f6f5151ec4f6aebec1f89b52e70dd464b818d26053e24 0.600000000000 1414457 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": 955181, "vin": [ { "gen": { "height": 955171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0de4736980908992595f6f5151ec4f6aebec1f89b52e70dd464b818d26053e24" } } ], "extra": [ 1, 19, 46, 51, 194, 207, 36, 254, 0, 252, 193, 214, 135, 244, 117, 44, 130, 165, 184, 196, 156, 223, 228, 4, 80, 169, 12, 208, 33, 244, 138, 239, 15, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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