Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c298cb1d14d108fd52ed7b9e6dc28081492070d642a4aa294f4110b82504614

Tx prefix hash: f6d55c01e1c181de112c802378b28b263d3d25dc29de6a89f87168eef39e6c15
Tx public key: f1ffe7da1a8e1059b3cc88d819218f0a35e4e9cf5ca173c82cd9aa4924eb953c
Timestamp: 1730904879 Timestamp [UCT]: 2024-11-06 14:54:39 Age [y:d:h:m:s]: 00:147:18:06:12
Block: 1147876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105421 RingCT/type: yes/0
Extra: 01f1ffe7da1a8e1059b3cc88d819218f0a35e4e9cf5ca173c82cd9aa4924eb953c0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f6c3a290e9f53cac7c4df30905024f35fd3a20ba586c3abe18ae869c4cbd7d5 0.600000000000 1632585 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": 1147886, "vin": [ { "gen": { "height": 1147876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f6c3a290e9f53cac7c4df30905024f35fd3a20ba586c3abe18ae869c4cbd7d5" } } ], "extra": [ 1, 241, 255, 231, 218, 26, 142, 16, 89, 179, 204, 136, 216, 25, 33, 143, 10, 53, 228, 233, 207, 92, 161, 115, 200, 44, 217, 170, 73, 36, 235, 149, 60, 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