Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e4f26f14d5d37bc22ae24cc661e3ab280663588cdc57df696be3a364710c802

Tx prefix hash: 986ec0e461b8180064f1e158b42a0767fb0b14e691cc7d960894131f3a54d66b
Tx public key: 0a10f7ad9087e4f6806109995a985799d2bc3ba0e1a00fc99b239340aedc5ef9
Timestamp: 1703572391 Timestamp [UCT]: 2023-12-26 06:33:11 Age [y:d:h:m:s]: 01:159:16:11:59
Block: 921362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375285 RingCT/type: yes/0
Extra: 010a10f7ad9087e4f6806109995a985799d2bc3ba0e1a00fc99b239340aedc5ef9021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16ffbad5acf68a7c5a0a1f22d1f20df5df94bfb22842d8b8994a8ec967932514 0.600000000000 1379048 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": 921372, "vin": [ { "gen": { "height": 921362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16ffbad5acf68a7c5a0a1f22d1f20df5df94bfb22842d8b8994a8ec967932514" } } ], "extra": [ 1, 10, 16, 247, 173, 144, 135, 228, 246, 128, 97, 9, 153, 90, 152, 87, 153, 210, 188, 59, 160, 225, 160, 15, 201, 155, 35, 147, 64, 174, 220, 94, 249, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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