Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 728f5cae042aa574e1c566bee10f8eb76bc05e237346942772f047fbb3e4eea0

Tx prefix hash: 0aa8e070a51f53e577cf7a2157c292022db7ba07c50d6dc19a4dcc3eb0ec1293
Tx public key: 55c3e2a45570a6cb7e8922ad79cc502fb4c49f0e043d34a8b3be1396834dc2a1
Timestamp: 1685603058 Timestamp [UCT]: 2023-06-01 07:04:18 Age [y:d:h:m:s]: 01:321:22:50:42
Block: 772638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491306 RingCT/type: yes/0
Extra: 0155c3e2a45570a6cb7e8922ad79cc502fb4c49f0e043d34a8b3be1396834dc2a102110000000175e3f0e9000000000000000000

1 output(s) for total of 1.690167470000 dcy

stealth address amount amount idx
00: 4e4d405f7354268af158f3d64285e9b9d002554a42eecdffedd0ffeb5545b386 1.690167470000 1222057 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": 772648, "vin": [ { "gen": { "height": 772638 } } ], "vout": [ { "amount": 1690167470, "target": { "key": "4e4d405f7354268af158f3d64285e9b9d002554a42eecdffedd0ffeb5545b386" } } ], "extra": [ 1, 85, 195, 226, 164, 85, 112, 166, 203, 126, 137, 34, 173, 121, 204, 80, 47, 180, 196, 159, 14, 4, 61, 52, 168, 179, 190, 19, 150, 131, 77, 194, 161, 2, 17, 0, 0, 0, 1, 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