Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 823eee2d3b1a6097bc6768114da755739ea9a1b5e165b01ef6abf795cf0a25e5

Tx prefix hash: 8847073bbf7fba88ae1e1e4ff94f792ae8b1e34515b69e8cabab74007fe44a3d
Tx public key: e01bfa5507fa62b06a99d9c45c54335df658112ea2b62b4f3be3c47cdbfa2100
Timestamp: 1722382808 Timestamp [UCT]: 2024-07-30 23:40:08 Age [y:d:h:m:s]: 00:251:07:23:09
Block: 1077306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179508 RingCT/type: yes/0
Extra: 01e01bfa5507fa62b06a99d9c45c54335df658112ea2b62b4f3be3c47cdbfa210002110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35e241e7dfd76cfc98fc5f8780746655a9229318550b7315e4126f2de7326ea2 0.600000000000 1549853 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": 1077316, "vin": [ { "gen": { "height": 1077306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35e241e7dfd76cfc98fc5f8780746655a9229318550b7315e4126f2de7326ea2" } } ], "extra": [ 1, 224, 27, 250, 85, 7, 250, 98, 176, 106, 153, 217, 196, 92, 84, 51, 93, 246, 88, 17, 46, 162, 182, 43, 79, 59, 227, 196, 124, 219, 250, 33, 0, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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