Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16fe30809fad8d10df826e88589c56ff05275bd20eb496eae8a7ec52eee686db

Tx prefix hash: 010f065ff3b769c0951e028e8b40762bbf8437e023eb5150df6b1e957c975d7c
Tx public key: e83b923bdc65bf720bdb2e8f8375155c40b38b118be20695bf1916265a1f7a6e
Timestamp: 1732932836 Timestamp [UCT]: 2024-11-30 02:13:56 Age [y:d:h:m:s]: 00:128:02:30:53
Block: 1164677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91347 RingCT/type: yes/0
Extra: 01e83b923bdc65bf720bdb2e8f8375155c40b38b118be20695bf1916265a1f7a6e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aacbaed6a290e3bb3e1f44852348266e8e46fd5fecb1841b97ab020858e8b681 0.600000000000 1650350 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": 1164687, "vin": [ { "gen": { "height": 1164677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aacbaed6a290e3bb3e1f44852348266e8e46fd5fecb1841b97ab020858e8b681" } } ], "extra": [ 1, 232, 59, 146, 59, 220, 101, 191, 114, 11, 219, 46, 143, 131, 117, 21, 92, 64, 179, 139, 17, 139, 226, 6, 149, 191, 25, 22, 38, 90, 31, 122, 110, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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