Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 176e8b98977b7fbb6ca4714715b505672d4c1cb2fcae04f03108249f21c1833d

Tx prefix hash: 7e1da64b30899a86cc6aaf2b689695e6a60a8fc083f01ff2b9aa92c94ed40ad1
Tx public key: 309249a9d17ba617b10a8f4c2f600ed72768dd604acd2f115563be626ba8c76c
Timestamp: 1728867821 Timestamp [UCT]: 2024-10-14 01:03:41 Age [y:d:h:m:s]: 00:197:19:09:24
Block: 1131083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141159 RingCT/type: yes/0
Extra: 01309249a9d17ba617b10a8f4c2f600ed72768dd604acd2f115563be626ba8c76c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e049b519f796c9af890ddbf64e600444f86c59d6fc1b2f0c7a8ccfe556dea601 0.600000000000 1613964 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": 1131093, "vin": [ { "gen": { "height": 1131083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e049b519f796c9af890ddbf64e600444f86c59d6fc1b2f0c7a8ccfe556dea601" } } ], "extra": [ 1, 48, 146, 73, 169, 209, 123, 166, 23, 177, 10, 143, 76, 47, 96, 14, 215, 39, 104, 221, 96, 74, 205, 47, 17, 85, 99, 190, 98, 107, 168, 199, 108, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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