Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aa98e921c59afadf6645186dc681e7b56c39edaf5d4bd523c105dd10302085c

Tx prefix hash: 818f10d091d128129a1d2a5f5e6c65a54f9df32c3666f5ca02cba9c3465cd232
Tx public key: a2cf78e089bbc3458bade02a8887fee86f79155a1b43d3de601e427332aeb1a6
Timestamp: 1741117193 Timestamp [UCT]: 2025-03-04 19:39:53 Age [y:d:h:m:s]: 00:009:16:58:16
Block: 1232166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6968 RingCT/type: yes/0
Extra: 01a2cf78e089bbc3458bade02a8887fee86f79155a1b43d3de601e427332aeb1a6021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6b8a6972b678af86b0d10c63c4e473f3b37b25beba5384bc0c3820c059d4319 0.600000000000 1719079 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": 1232176, "vin": [ { "gen": { "height": 1232166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6b8a6972b678af86b0d10c63c4e473f3b37b25beba5384bc0c3820c059d4319" } } ], "extra": [ 1, 162, 207, 120, 224, 137, 187, 195, 69, 139, 173, 224, 42, 136, 135, 254, 232, 111, 121, 21, 90, 27, 67, 211, 222, 96, 30, 66, 115, 50, 174, 177, 166, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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