Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b98fe99afbf5c8ebe5fa1cd2af4c0346b6dd7536922f59fe0a74f6568943ae6c

Tx prefix hash: 474137ae5e64dbe96de7263de05441d44a98886457e0b7914dff18f6cc14daa6
Tx public key: d721c1ea36eb923642ae973e7d2bcaedb37e75eab23992fff614e11ef8bf0665
Timestamp: 1735226631 Timestamp [UCT]: 2024-12-26 15:23:51 Age [y:d:h:m:s]: 00:088:07:34:05
Block: 1183668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62895 RingCT/type: yes/0
Extra: 01d721c1ea36eb923642ae973e7d2bcaedb37e75eab23992fff614e11ef8bf06650211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7178ee9c31c84525f81c2d9de8b805c6f09416fe393c0f5f571cd226effac76f 0.600000000000 1670115 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": 1183678, "vin": [ { "gen": { "height": 1183668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7178ee9c31c84525f81c2d9de8b805c6f09416fe393c0f5f571cd226effac76f" } } ], "extra": [ 1, 215, 33, 193, 234, 54, 235, 146, 54, 66, 174, 151, 62, 125, 43, 202, 237, 179, 126, 117, 234, 178, 57, 146, 255, 246, 20, 225, 30, 248, 191, 6, 101, 2, 17, 0, 0, 0, 5, 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