Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1189d51212b386aa649026c4c3e0e809762b21303ca212b11ad9725d9cdce681

Tx prefix hash: c6ee8ff8db4eae24c00ccb64cbdb53336cc4f20b7c0c4028cbd24aca0eed780c
Tx public key: 3579d168fb28189de86d4fee49fb08f2f6a1e28d991e6cdab86bb0819a087852
Timestamp: 1736469741 Timestamp [UCT]: 2025-01-10 00:42:21 Age [y:d:h:m:s]: 00:075:12:03:55
Block: 1193965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53718 RingCT/type: yes/0
Extra: 013579d168fb28189de86d4fee49fb08f2f6a1e28d991e6cdab86bb0819a0878520211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90597dca6e206409b8d8f5847fa363a5b2abe297c2f0eac20da888a46bf0a969 0.600000000000 1680530 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": 1193975, "vin": [ { "gen": { "height": 1193965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90597dca6e206409b8d8f5847fa363a5b2abe297c2f0eac20da888a46bf0a969" } } ], "extra": [ 1, 53, 121, 209, 104, 251, 40, 24, 157, 232, 109, 79, 238, 73, 251, 8, 242, 246, 161, 226, 141, 153, 30, 108, 218, 184, 107, 176, 129, 154, 8, 120, 82, 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