Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af02abc6a39dccfe9b27bbc459a62ed1670d7985290960d93f3aea6dbc5a0c2a

Tx prefix hash: 197ebd4f924d894a9e2a68de417e32bc2a6e4c039fb740bbe4a0f66b69cd7aa1
Tx public key: 068389ab2e6c2992abddfbcef80e6a4b431cc0ceae986de8976dd22fc810b22e
Timestamp: 1718390408 Timestamp [UCT]: 2024-06-14 18:40:08 Age [y:d:h:m:s]: 00:321:23:41:10
Block: 1044225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230106 RingCT/type: yes/0
Extra: 01068389ab2e6c2992abddfbcef80e6a4b431cc0ceae986de8976dd22fc810b22e02110000000ac663bcf3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 094ca32aa6542e415ee5b597d6871a9c002bff66f2f4f4294dce71626a15c2bb 0.600000000000 1513472 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": 1044235, "vin": [ { "gen": { "height": 1044225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "094ca32aa6542e415ee5b597d6871a9c002bff66f2f4f4294dce71626a15c2bb" } } ], "extra": [ 1, 6, 131, 137, 171, 46, 108, 41, 146, 171, 221, 251, 206, 248, 14, 106, 75, 67, 28, 192, 206, 174, 152, 109, 232, 151, 109, 210, 47, 200, 16, 178, 46, 2, 17, 0, 0, 0, 10, 198, 99, 188, 243, 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