Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 512e243c2973505ea8a7d69e9602a72be4660994651f982fef923455d7252bd6

Tx prefix hash: d0a901276bc0a9015cbbdb101ea36c91544904462615156a02bb4fb08c6ffb2d
Tx public key: 0b6e4dde3d7494fb5ee6511dec370e45108fc83f9b1a5450e3c89317d8fe4b4f
Timestamp: 1635537482 Timestamp [UCT]: 2021-10-29 19:58:02 Age [y:d:h:m:s]: 03:059:02:45:28
Block: 363156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 820725 RingCT/type: yes/0
Extra: 010b6e4dde3d7494fb5ee6511dec370e45108fc83f9b1a5450e3c89317d8fe4b4f021100000001a272b9cb000000000000000000

1 output(s) for total of 38.433844004000 dcy

stealth address amount amount idx
00: 4a80246e7838453195c57969e1d34812971d009b27f906720de81f7f76474663 38.433844004000 738208 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": 363166, "vin": [ { "gen": { "height": 363156 } } ], "vout": [ { "amount": 38433844004, "target": { "key": "4a80246e7838453195c57969e1d34812971d009b27f906720de81f7f76474663" } } ], "extra": [ 1, 11, 110, 77, 222, 61, 116, 148, 251, 94, 230, 81, 29, 236, 55, 14, 69, 16, 143, 200, 63, 155, 26, 84, 80, 227, 200, 147, 23, 216, 254, 75, 79, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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