Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37b568a1c5ceba4e27f0d2720ffd46b80aa1964cd8eba989f4275a2b5946b33f

Tx prefix hash: 72af61f60790784ca3c8a7d9dd7e4daad72c126546859c96e2f99a673217ccff
Tx public key: a93784b986effc8425a3cc8ee4b310d2b114e3fd9bd51dbf03ab276f84830102
Timestamp: 1657945192 Timestamp [UCT]: 2022-07-16 04:19:52 Age [y:d:h:m:s]: 02:249:00:38:38
Block: 544739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 699164 RingCT/type: yes/0
Extra: 01a93784b986effc8425a3cc8ee4b310d2b114e3fd9bd51dbf03ab276f8483010202110000000c5eb576c5000000000000000000

1 output(s) for total of 9.617311903000 dcy

stealth address amount amount idx
00: c856413d22e75e9a282a3888fdaa7d0f9b3e85fd9a0c6e44558cc152e7996bd8 9.617311903000 975552 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": 544749, "vin": [ { "gen": { "height": 544739 } } ], "vout": [ { "amount": 9617311903, "target": { "key": "c856413d22e75e9a282a3888fdaa7d0f9b3e85fd9a0c6e44558cc152e7996bd8" } } ], "extra": [ 1, 169, 55, 132, 185, 134, 239, 252, 132, 37, 163, 204, 142, 228, 179, 16, 210, 177, 20, 227, 253, 155, 213, 29, 191, 3, 171, 39, 111, 132, 131, 1, 2, 2, 17, 0, 0, 0, 12, 94, 181, 118, 197, 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