Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ff0b2aa674358c9641ce593fd1104f738940ce4e300d95d9a987569c5d71e8

Tx prefix hash: 66400c420706827d136529d4c6f10410babf8c14580f0259e1d732cc28f95847
Tx public key: 811a37892689d6bed9dda8c0e27de53d8ec5d9070fd91d2e91fa2c12c2cc720a
Timestamp: 1713708108 Timestamp [UCT]: 2024-04-21 14:01:48 Age [y:d:h:m:s]: 00:207:05:08:28
Block: 1005390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148345 RingCT/type: yes/0
Extra: 01811a37892689d6bed9dda8c0e27de53d8ec5d9070fd91d2e91fa2c12c2cc720a0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d9f8568f0f24afe621b6cdb02b771b62d4ce71c4286b83d5f70359419f80d60 0.600000000000 1466040 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": 1005400, "vin": [ { "gen": { "height": 1005390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d9f8568f0f24afe621b6cdb02b771b62d4ce71c4286b83d5f70359419f80d60" } } ], "extra": [ 1, 129, 26, 55, 137, 38, 137, 214, 190, 217, 221, 168, 192, 226, 125, 229, 61, 142, 197, 217, 7, 15, 217, 29, 46, 145, 250, 44, 18, 194, 204, 114, 10, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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