Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e50ad261e31d0d110365a3bcb3a308091b62b47118bc438a1b3a15b62f020680

Tx prefix hash: 7108ab85c4b7e7a1c49c6ecb8227caa2ff275adbf484048f1675542518813ddc
Tx public key: ab21c61afec564da04601a5e403c7f27f7c3db64c2c97c9b8a5e419ef2ac9c39
Timestamp: 1636333385 Timestamp [UCT]: 2021-11-08 01:03:05 Age [y:d:h:m:s]: 03:050:21:16:58
Block: 369647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 814933 RingCT/type: yes/0
Extra: 01ab21c61afec564da04601a5e403c7f27f7c3db64c2c97c9b8a5e419ef2ac9c3902110000001f4f792ffd000000000000000000

1 output(s) for total of 36.576861349000 dcy

stealth address amount amount idx
00: 751a1bad976dcc497b06aff08bcdfaab6719d7e74c69eaa02edc349890084842 36.576861349000 749517 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": 369657, "vin": [ { "gen": { "height": 369647 } } ], "vout": [ { "amount": 36576861349, "target": { "key": "751a1bad976dcc497b06aff08bcdfaab6719d7e74c69eaa02edc349890084842" } } ], "extra": [ 1, 171, 33, 198, 26, 254, 197, 100, 218, 4, 96, 26, 94, 64, 60, 127, 39, 247, 195, 219, 100, 194, 201, 124, 155, 138, 94, 65, 158, 242, 172, 156, 57, 2, 17, 0, 0, 0, 31, 79, 121, 47, 253, 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