Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f0489331030b9ec6a6dc953b3c5ce9ab47453dbc79024bc98dff13d518cb00

Tx prefix hash: 206f3e9df1d0ad84e8c5279ac3f679846c47db18c432aea41326998d08890609
Tx public key: 46e33ed70a56f03a2c36fe42b2ea11d40833ed6a835425ad444c99b61910a8e8
Timestamp: 1725275255 Timestamp [UCT]: 2024-09-02 11:07:35 Age [y:d:h:m:s]: 00:228:03:45:42
Block: 1101287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162928 RingCT/type: yes/0
Extra: 0146e33ed70a56f03a2c36fe42b2ea11d40833ed6a835425ad444c99b61910a8e8021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff8eb9cddaedfe9c9d5bd93afd1632eab09eb266aa8241dbbf94683ede614f9a 0.600000000000 1577280 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": 1101297, "vin": [ { "gen": { "height": 1101287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff8eb9cddaedfe9c9d5bd93afd1632eab09eb266aa8241dbbf94683ede614f9a" } } ], "extra": [ 1, 70, 227, 62, 215, 10, 86, 240, 58, 44, 54, 254, 66, 178, 234, 17, 212, 8, 51, 237, 106, 131, 84, 37, 173, 68, 76, 153, 182, 25, 16, 168, 232, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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