Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f1e9bc5ce9bebd1dcf2eb66c48e40fdf3ac5dc7eb559ff6b465c8d767509fcd

Tx prefix hash: e3128a8c2df60e2bdb9c27f4c899e6f395c30e3dfc5921b7dc29d4d61cd821aa
Tx public key: ccee82435a1d8a8cc9104463712779221e9bc7cc469777c698c43edd0e282d06
Timestamp: 1735303177 Timestamp [UCT]: 2024-12-27 12:39:37 Age [y:d:h:m:s]: 00:176:08:48:03
Block: 1184289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125728 RingCT/type: yes/0
Extra: 01ccee82435a1d8a8cc9104463712779221e9bc7cc469777c698c43edd0e282d060211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 101003c9c665a4d41a3fc013f8eb6c36541c2ea461396d76182597daf0c79bd1 0.600000000000 1670746 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": 1184299, "vin": [ { "gen": { "height": 1184289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "101003c9c665a4d41a3fc013f8eb6c36541c2ea461396d76182597daf0c79bd1" } } ], "extra": [ 1, 204, 238, 130, 67, 90, 29, 138, 140, 201, 16, 68, 99, 113, 39, 121, 34, 30, 155, 199, 204, 70, 151, 119, 198, 152, 196, 62, 221, 14, 40, 45, 6, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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