Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c897fff7172e3620fbcb9cb625e7fa169cc1103eb97cb18b178c469c7592887

Tx prefix hash: 2eec45b80d381b24dc010bce537051f2ebce10ec3f0f08ecae929a89724d2014
Tx public key: 523eb854bfd4bcad8c254f4543a0b5b8caa2957fe444c8d26a7de51bfeed6df3
Timestamp: 1720794179 Timestamp [UCT]: 2024-07-12 14:22:59 Age [y:d:h:m:s]: 00:180:15:03:42
Block: 1064155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129234 RingCT/type: yes/0
Extra: 01523eb854bfd4bcad8c254f4543a0b5b8caa2957fe444c8d26a7de51bfeed6df302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ad861a1d4f8c373c6086f18e0800b691140abd098d2c4a308627ed0f6693231 0.600000000000 1534678 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": 1064165, "vin": [ { "gen": { "height": 1064155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ad861a1d4f8c373c6086f18e0800b691140abd098d2c4a308627ed0f6693231" } } ], "extra": [ 1, 82, 62, 184, 84, 191, 212, 188, 173, 140, 37, 79, 69, 67, 160, 181, 184, 202, 162, 149, 127, 228, 68, 200, 210, 106, 125, 229, 27, 254, 237, 109, 243, 2, 17, 0, 0, 0, 1, 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