Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d52689b3d9680be20ca611a2cd82d7015bf4dd30bd04f05b24d70ed58358f85d

Tx prefix hash: e77d054c69eeb6babba0a19d4baf4929c6b9ed45c23c3c71a14fb893434f6f09
Tx public key: 86532bca72377fd53dfbcad821fe0662acbf2b45c6d4e64ceeae7d048d99fda0
Timestamp: 1734902884 Timestamp [UCT]: 2024-12-22 21:28:04 Age [y:d:h:m:s]: 00:087:00:49:40
Block: 1181022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61976 RingCT/type: yes/0
Extra: 0186532bca72377fd53dfbcad821fe0662acbf2b45c6d4e64ceeae7d048d99fda00211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87abe7e5458372057e036668d4c0f149c0500f7938061eeae1baed23d1349ce8 0.600000000000 1667437 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": 1181032, "vin": [ { "gen": { "height": 1181022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87abe7e5458372057e036668d4c0f149c0500f7938061eeae1baed23d1349ce8" } } ], "extra": [ 1, 134, 83, 43, 202, 114, 55, 127, 213, 61, 251, 202, 216, 33, 254, 6, 98, 172, 191, 43, 69, 198, 212, 230, 76, 238, 174, 125, 4, 141, 153, 253, 160, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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