Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d347c34b08b800d6134313f905d534d87fd3855a69ba213ba8a97858a47f3777

Tx prefix hash: 183a44ad5a0b10e5d8ce2bdc2326bc9790bd7dddfbca31dd9be75a678ee33f1c
Tx public key: 4eb68c1d10f9913b24f79bbc4f8942b0d9f5985327a63a70fa9ff3c9f89709bf
Timestamp: 1703344345 Timestamp [UCT]: 2023-12-23 15:12:25 Age [y:d:h:m:s]: 01:322:16:19:32
Block: 919470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489466 RingCT/type: yes/0
Extra: 014eb68c1d10f9913b24f79bbc4f8942b0d9f5985327a63a70fa9ff3c9f89709bf02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1e1218cc27d3dd28fdb4be05859026e612d1d7199ed9314ca7e4dcb1177e48f 0.600000000000 1377144 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": 919480, "vin": [ { "gen": { "height": 919470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1e1218cc27d3dd28fdb4be05859026e612d1d7199ed9314ca7e4dcb1177e48f" } } ], "extra": [ 1, 78, 182, 140, 29, 16, 249, 145, 59, 36, 247, 155, 188, 79, 137, 66, 176, 217, 245, 152, 83, 39, 166, 58, 112, 250, 159, 243, 201, 248, 151, 9, 191, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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