Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6049cdca76402a2a2d89eda0d669eeb908b02b8d7073df14529fd36be4bb8e24

Tx prefix hash: 2ff7c21d7a228395380ef1d28bf9e2fbf83ef12e070cde957afc83dfc39b9c51
Tx public key: 2ae6e2aeac633e049937328690c6e250f9adaa58b6f836846c186fd66afee410
Timestamp: 1725534755 Timestamp [UCT]: 2024-09-05 11:12:35 Age [y:d:h:m:s]: 00:047:17:17:15
Block: 1103444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34147 RingCT/type: yes/0
Extra: 012ae6e2aeac633e049937328690c6e250f9adaa58b6f836846c186fd66afee410021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5d756ee99a56272807202e8bf51da630db1fd54d9a3e3934fe281b115b31613 0.600000000000 1580277 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": 1103454, "vin": [ { "gen": { "height": 1103444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5d756ee99a56272807202e8bf51da630db1fd54d9a3e3934fe281b115b31613" } } ], "extra": [ 1, 42, 230, 226, 174, 172, 99, 62, 4, 153, 55, 50, 134, 144, 198, 226, 80, 249, 173, 170, 88, 182, 248, 54, 132, 108, 24, 111, 214, 106, 254, 228, 16, 2, 17, 0, 0, 0, 1, 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