Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32bb3b06d4c467b0715acf3933f39c21a6d174409a647b67a23a988c6185a903

Tx prefix hash: 9909771bfface12a1a857a09dbc2fa8f03a43c37bea92ab9e354b535aacfea05
Tx public key: 31e8e4b4bed111e75bab21ff713fb75a4835d59dea6e4f2af4c19bd2ad165253
Timestamp: 1737360344 Timestamp [UCT]: 2025-01-20 08:05:44 Age [y:d:h:m:s]: 00:304:12:27:19
Block: 1201278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215193 RingCT/type: yes/0
Extra: 0131e8e4b4bed111e75bab21ff713fb75a4835d59dea6e4f2af4c19bd2ad1652530211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5dec30637f1f87e982b27887d443f9ee6ecfdabc2db7c8a8e3d70dae482a847 0.600000000000 1687927 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": 1201288, "vin": [ { "gen": { "height": 1201278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5dec30637f1f87e982b27887d443f9ee6ecfdabc2db7c8a8e3d70dae482a847" } } ], "extra": [ 1, 49, 232, 228, 180, 190, 209, 17, 231, 91, 171, 33, 255, 113, 63, 183, 90, 72, 53, 213, 157, 234, 110, 79, 42, 244, 193, 155, 210, 173, 22, 82, 83, 2, 17, 0, 0, 0, 3, 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