Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342439e447b3f63d358ce9135f60eae138d8186bc6fb8265b6a35b4642a307d1

Tx prefix hash: f47f2413d89c41e9c6372e9e55f11b70d36b262f37bb7ba74fadc384fa0939c3
Tx public key: b1625d23140a939aea1b820e03c70739a4c0cc1f6c1d93a7b2c29399fadbd954
Timestamp: 1715976516 Timestamp [UCT]: 2024-05-17 20:08:36 Age [y:d:h:m:s]: 00:315:08:23:57
Block: 1024203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225392 RingCT/type: yes/0
Extra: 01b1625d23140a939aea1b820e03c70739a4c0cc1f6c1d93a7b2c29399fadbd9540211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b23449cee8fe5947dad2e39be3777a606583155e7cdc5292156e8e3f95f508f6 0.600000000000 1489762 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": 1024213, "vin": [ { "gen": { "height": 1024203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b23449cee8fe5947dad2e39be3777a606583155e7cdc5292156e8e3f95f508f6" } } ], "extra": [ 1, 177, 98, 93, 35, 20, 10, 147, 154, 234, 27, 130, 14, 3, 199, 7, 57, 164, 192, 204, 31, 108, 29, 147, 167, 178, 194, 147, 153, 250, 219, 217, 84, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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