Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e216cabc9b457efe88d2e3acc6795bd6a27aba13dd07e8b0603353a19986dae

Tx prefix hash: ab95a49e12f07d30b49446d106ef0e02a69466936a59fc0d7580bccd8fcdc24c
Tx public key: 539ba28d7ef88aaba156b4b1f4d5d0a1a6bd356583995f7d86b3b7bf25bf4567
Timestamp: 1728247810 Timestamp [UCT]: 2024-10-06 20:50:10 Age [y:d:h:m:s]: 00:173:20:27:58
Block: 1125929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124047 RingCT/type: yes/0
Extra: 01539ba28d7ef88aaba156b4b1f4d5d0a1a6bd356583995f7d86b3b7bf25bf456702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5765bfd4776fbc6d23a34fc0f37675ea768a95de8dca689e863a6c7d7453322b 0.600000000000 1608702 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": 1125939, "vin": [ { "gen": { "height": 1125929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5765bfd4776fbc6d23a34fc0f37675ea768a95de8dca689e863a6c7d7453322b" } } ], "extra": [ 1, 83, 155, 162, 141, 126, 248, 138, 171, 161, 86, 180, 177, 244, 213, 208, 161, 166, 189, 53, 101, 131, 153, 95, 125, 134, 179, 183, 191, 37, 191, 69, 103, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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