Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c142868906aec4aa647a92dbe248c32965c6be15c2fec79a96f8e9f8aa2ffb94

Tx prefix hash: 4c339c94f54128e6ba66839e3c6bbc69a6213608212d52f4c5728eead08e33bb
Tx public key: 245d3906b40261e56c0c313eb25c396d704d1fd67b3852bd3fa789574335f229
Timestamp: 1733773541 Timestamp [UCT]: 2024-12-09 19:45:41 Age [y:d:h:m:s]: 00:108:16:50:46
Block: 1171648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77477 RingCT/type: yes/0
Extra: 01245d3906b40261e56c0c313eb25c396d704d1fd67b3852bd3fa789574335f229021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6c60e825fb30dcb4ee9db8fa2023568b070b0e4185df158a6cffe9ecc3bd521 0.600000000000 1657431 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": 1171658, "vin": [ { "gen": { "height": 1171648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6c60e825fb30dcb4ee9db8fa2023568b070b0e4185df158a6cffe9ecc3bd521" } } ], "extra": [ 1, 36, 93, 57, 6, 180, 2, 97, 229, 108, 12, 49, 62, 178, 92, 57, 109, 112, 77, 31, 214, 123, 56, 82, 189, 63, 167, 137, 87, 67, 53, 242, 41, 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