Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342e242e1160f5a29d1e66eb0182557f17298cd3802e29558d362b436c2a9539

Tx prefix hash: aa37b0f428562d0e64d8b931d64a1f068623afe7e81b43f3bd94ea3f95a83691
Tx public key: e40ed32f12f0ecd97b961d7df73ee3b041ee8a3347d13f16e4b38f0505c16ef8
Timestamp: 1699604080 Timestamp [UCT]: 2023-11-10 08:14:40 Age [y:d:h:m:s]: 01:140:11:44:51
Block: 888472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361586 RingCT/type: yes/0
Extra: 01e40ed32f12f0ecd97b961d7df73ee3b041ee8a3347d13f16e4b38f0505c16ef8021100000004faf35c9c000000000000000000

1 output(s) for total of 0.698430895000 dcy

stealth address amount amount idx
00: 96ae54a57e70afc43227c03b686abb1a7fd906dc177a7b8648ca2081db5bbe14 0.698430895000 1344415 of 0

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": 888482, "vin": [ { "gen": { "height": 888472 } } ], "vout": [ { "amount": 698430895, "target": { "key": "96ae54a57e70afc43227c03b686abb1a7fd906dc177a7b8648ca2081db5bbe14" } } ], "extra": [ 1, 228, 14, 211, 47, 18, 240, 236, 217, 123, 150, 29, 125, 247, 62, 227, 176, 65, 238, 138, 51, 71, 209, 63, 22, 228, 179, 143, 5, 5, 193, 110, 248, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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