Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c93a660e74f298e84cf033d204086822ca63c101e1d3d8fc79bc84d0ece8b67

Tx prefix hash: 697330f4e2156ae9cec794e177c72696eb83059cb679fa00cf5d1a649e8e1b9a
Tx public key: 9634543c7b84d0f585c7905266f44a5dc8bb978e728bafdd3fba0def88bcc25f
Timestamp: 1717867867 Timestamp [UCT]: 2024-06-08 17:31:07 Age [y:d:h:m:s]: 00:228:01:32:42
Block: 1039878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163166 RingCT/type: yes/0
Extra: 019634543c7b84d0f585c7905266f44a5dc8bb978e728bafdd3fba0def88bcc25f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac84f87d8e2503f49dfdb8fecaaccca09a4371210f419f8743f3408ea720540f 0.600000000000 1508533 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": 1039888, "vin": [ { "gen": { "height": 1039878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac84f87d8e2503f49dfdb8fecaaccca09a4371210f419f8743f3408ea720540f" } } ], "extra": [ 1, 150, 52, 84, 60, 123, 132, 208, 245, 133, 199, 144, 82, 102, 244, 74, 93, 200, 187, 151, 142, 114, 139, 175, 221, 63, 186, 13, 239, 136, 188, 194, 95, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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